📘 Free PROFESSIONAL-CLOUD-DEVOPS-ENGINEER Sample Questions
You support a Node.js application running on Google Kubernetes Engine (GKE) in production. The application makes
several HTTP requests to dependent applications. You want to anticipate which dependent applications might cause
performance issues. What should you do?
A
Instrument all applications with Stackdriver Profiler.
B
Instrument all applications with Stackdriver Trace and review inter-service HTTP requests.
C
Use Stackdriver Debugger to review the execution of logic within each application to instrument all
applications.
D
Modify the Node.js application to log HTTP request and response times to dependent applications. Use
Stackdriver Logging to find dependent applications that are performing poorly.
Correct Answer:
B. Instrument all applications with Stackdriver Trace and review inter-service HTTP requests.
Explanation:
Stackdriver Trace allows you to collect and analyze performance data for all the applications that make up your
system, including the applications running on GKE. By instrumenting your application with Stackdriver Trace, you can
see detailed performance information for each request, including the time spent in each component of your system,
as well as any inter-service HTTP requests. This will allow you to identify which dependent applications might be
causing performance issues, so that you can focus on optimizing those services specifically.
You created a Stackdriver chart for CPU utilization in a dashboard within your workspace project. You want to share
the chart with your Site Reliability Engineering
(SRE) team only. You want to ensure you follow the principle of least privilege. What should you do?
A
Share the workspace Project ID with the SRE team. Assign the SRE team the Monitoring Viewer IAM role
in the workspace project.
B
Share the workspace Project ID with the SRE team. Assign the SRE team the Dashboard Viewer IAM role in
the workspace project.
C
Click ג €Share chart by URLג€ and provide the URL to the SRE team. Assign the SRE team the Monitoring
Viewer IAM role in the workspace project.
D
Click ג€Share chart by URLג€ and provide the URL to the SRE team. Assign the SRE team the Dashboard
Viewer IAM role in the workspace project.
Correct Answer:
C. Click ג €Share chart by URLג€ and provide the URL to the SRE team. Assign the SRE team the Monitoring
Viewer IAM role in the workspace project.
Explanation:
This option allows you to share the specific chart with the SRE team only, granting them read-only access to the
chart's data, this way the team can view the CPU utilization chart and troubleshoot any performance issues related
to the chart. You can use the feature of "Share chart by URL" to share the specific chart with the SRE team only, and
provide a secure URL that can only be access by members of the team. And also giving them the "Monitoring
Viewer" role, will give them just enough privilege to see the chart and its data but not the ability to make changes to
the project, dashboard or other charts.
Your organization wants to implement Site Reliability Engineering (SRE) culture and principles. Recently, a service
that you support had a limited outage. A manager on another team asks you to provide a formal explanation of what
happened so they can action remediations. What should you do?
A
Develop a postmortem that includes the root causes, resolution, lessons learned, and a prioritized list of
action items. Share it with the manager only.
B
Develop a postmortem that includes the root causes, resolution, lessons learned, and a prioritized list of
action items. Share it on the engineering organization's document portal.
C
Develop a postmortem that includes the root causes, resolution, lessons learned, the list of people
responsible, and a list of action items for each person. Share it with the manager only.
D
Develop a postmortem that includes the root causes, resolution, lessons learned, the list of people
responsible, and a list of action items for each person. Share it on the engineering organization's document
portal.
Correct Answer:
B. Develop a postmortem that includes the root causes, resolution, lessons learned, and a prioritized list of
action items. Share it on the engineering organization's document portal.
Explanation:
GKE's default logging agent provides a managed solution to deploy and manage the agents that send the logs for
your clusters to Cloud Logging. Depending on your GKE cluster master version, either fluentd or fluentbit are used to
collect logs. Starting from GKE 1.17, logs are collected using a fluentbit-based agent. GKE clusters using versions prior
to GKE 1.17 use a fluentd-based agent. If you want to alter the default behavior of the fluentdagents, then you can
run a customized fluentd agent or a customized fluentbit agent.
Reference:
https://cloud.google.com/stackdriver/docs/solutions/gke/managing-logs
You have a set of applications running on a Google Kubernetes Engine (GKE) cluster, and you are using Stackdriver
Kubernetes Engine Monitoring. You are bringing a new containerized application required by your company into
production. This application is written by a third party and cannot be modified or reconfigured. The application
writes its log information to /var/log/app_messages.log, and you want to send these log entries to Stackdriver
Logging. What should you do?
A
Use the default Stackdriver Kubernetes Engine Monitoring agent configuration.
B
Deploy a Fluentd daemonset to GKE. Then create a customized input and output configuration to tail the
log file in the application's pods and write to Stackdriver Logging.
C
Install Kubernetes on Google Compute Engine (GCE) and redeploy your applications. Then customize the
built-in Stackdriver Logging configuration to tail the log file in the application's pods and write to Stackdriver
Logging.
D
Write a script to tail the log file within the pod and write entries to standard output. Run the script as a
sidecar container with the application's pod. Configure a shared volume between the containers to allow the
script to have read access to /var/log in the application container.
Correct Answer:
B. Deploy a Fluentd daemonset to GKE. Then create a customized input and output configuration to tail the
log file in the application's pods and write to Stackdriver Logging.
Explanation:
Besides the list of default logs that the Logging agent streams by default, you can customize the Logging agent to
send additional logs to Logging or to adjust agent settings by adding input configurations. The configuration
definitions in these sections apply to the fluent-plugin-google-cloud output plugin only and specify how logs are
transformed and ingested into Cloud Logging.
You are running an application in a virtual machine (VM) using a custom Debian image. The image has the
Stackdriver Logging agent installed. The VM has the cloud-platform scope. The application is logging information via
syslog. You want to use Stackdriver Logging in the Google Cloud Platform Console to visualize the logs. You notice
that syslog is not showing up in the "All logs" dropdown list of the Logs Viewer. What is the first thing you should do?
A
Look for the agent's test log entry in the Logs Viewer
B
Install the most recent version of the Stackdriver agent.
C
Verify the VM service account access scope includes the monitoring.write scope.
D
SSH to the VM and execute the following commands on your VM: ps ax | grep fluentd.
Correct Answer:
D. SSH to the VM and execute the following commands on your VM: ps ax | grep fluentd.
Explanation:
When an instance is created, we can specify which service account the instance uses when calling Google Cloud APIs.
The instance is automatically configured with access scope and one such access scope is monitoring.write (Link :
https://cloud.google.com/compute/docs/access/service-read
is to publish metric data and logging.write is to write compute engine logs.
You use a multiple step Cloud Build pipeline to build and deploy your application to Google Kubernetes Engine (GKE).
You want to integrate with a third-party monitoring platform by performing a HTTP POST of the build information to
a webhook. You want to minimize the development effort. What should you do?
A
Add logic to each Cloud Build step to HTTP POST the build information to a webhook.
B
Add a new step at the end of the pipeline in Cloud Build to HTTP POST the build information to a
webhook.
C
Use Stackdriver Logging to create a logs-based metric from the Cloud Build logs. Create an Alert with a
Webhook notification type.
D
Create a Cloud Pub/Sub push subscription to the Cloud Build cloud-builds PubSub topic to HTTP POST the
build information to a webhook.
Correct Answer:
D. Create a Cloud Pub/Sub push subscription to the Cloud Build cloud-builds PubSub topic to HTTP POST the
build information to a webhook.
Explanation:
Cloud Build publishes messages on a Google Pub/Sub topic when your build's state changes, such as when your build
is created, when your build transitions to a working state, and when your build completes. The Pub/Sub topic to
which Cloud Build publishes these build update messages is called cloud-builds. Each message contains a base64
JSON string representation of your Build resource in the message.data attribute. The build's unique ID and the build's
status can be found in the message.attributes field. You can use a push or pull model for your Pub/Sub subscriptions.
Push subscriptions deliver messages to an HTTP endpoint that you define. Messages are delivered as soon as they
are published to the topic.
You use Spinnaker to deploy your application and have created a canary deployment stage in the pipeline. Your
application has an in-memory cache that loads objects at start time. You want to automate the comparison of the
canary version against the production version. How should you configure the canary analysis?
A
Compare the canary with a new deployment of the current production version.
B
Compare the canary with a new deployment of the previous production version.
C
Compare the canary with the existing deployment of the current production version
D
Compare the canary with the average performance of a sliding window of previous production versions.
Correct Answer:
A. Compare the canary with a new deployment of the current production version.
Explanation:
Reference:
https://cloud.google.com/architecture/automated-canary-analysis-kubernetes-engine-spinnaker
https://spinnaker.io/guides/user/canary/best-practices/#compare-canary-against-baseline-not-against-production
You deploy a new release of an internal application during a weekend maintenance window when there is minimal
user tragic. After the window ends, you learn that one of the new features isn't working as expected in the
production environment. After an extended outage, you roll back the new release and deploy a fix.
You want to modify your release process to reduce the mean time to recovery so you can avoid extended outages in
the future. What should you do? (Choose two.)
A
Before merging new code, require 2 different peers to review the code changes.
B
Adopt the blue/green deployment strategy when releasing new code via a CD server.
C
Integrate a code linting tool to validate coding standards before any code is accepted into the repository
D
Integrate a code linting tool to validate coding standards before any code is accepted into the repository
E
Configure a CI server. Add a suite of unit tests to your code and have your CI server run them on commit
and verify any changes.
Correct Answer:
B. Adopt the blue/green deployment strategy when releasing new code via a CD server.
You have a pool of application servers running on Compute Engine. You need to provide a secure solution that
requires the least amount of configuration and allows developers to easily access application logs for
troubleshooting. How would you implement the solution on GCP?
A
ג€¢ Deploy the Stackdriver logging agent to the application servers. ג €¢ Give the developers the IAM Logs Viewer role to access Stackdriver and view logs.
B
ג€¢ Deploy the Stackdriver logging agent to the application servers. ג €¢ Give the developers the IAM Logs
Private Logs Viewer role to access Stackdriver and view logs.
C
ג€¢ Deploy the Stackdriver monitoring agent to the application servers. ג €¢ Give the developers the IAM
Monitoring Viewer role to access Stackdriver and view metrics.
D
ג€¢ Install the gsutil command line tool on your application servers. ג €¢ Write a script using gsutil to
upload your application log to a Cloud Storage bucket, and then schedule it to run via cron every 5 minutes.
ג€¢ Give the developers the IAM Object Viewer access to view the logs in the specified bucket.
Correct Answer:
A. ג€¢ Deploy the Stackdriver logging agent to the application servers. ג €¢ Give the developers the IAM Logs Viewer role to access Stackdriver and view logs.
Explanation:
Reference:
https://cloud.google.com/logging/docs/access-control
You support the backend of a mobile phone game that runs on a Google Kubernetes Engine (GKE) cluster. The
application is serving HTTP requests from users.
You need to implement a solution that will reduce the network cost. What should you do?
A
Configure the VPC as a Shared VPC Host project.
B
Configure your network services on the Standard Tier.
C
Configure your Kubernetes cluster as a Private Cluster.
D
Configure a Google Cloud HTTP Load Balancer as Ingress.
Correct Answer:
B. Configure your network services on the Standard Tier.
Questions: 1-10 out of 239
Continue Full Practice..
GET ALL 239 QUESTIONS